2015-01-23 - 16744 - BreakFix - Hot Market Program Issues. #ProductionBreakFix #abaphotmarket #HotMarket

32015-01-23 - 16744- Service Request - Hot Market Program Issues

Problem Summary


Hot Market Program Issues

Admin Info



Purpose
Hot Market Program Issues
Requested by
Jeffrey Mau
Issue Date
01-23-2015
Resolved by
Surya,Venkat,Siba
Resolved Date

Document Status
Complete

Estimates



Sl.No
Activity
Estimation in Hours
1
Research
5
2
Documentation
4
3
Development
4
4
Unit test in DEV
2
5
Unit test in QUA
2
6
Other activity
NA

TOTAL
17

Detailed Problem Description

(Include Screen Shots if required )

It is observed that Hot Market Program is facing Packing Issues.
1) Packing is missing for Some Deliveries randomly when the HOT market program is run with transaction ZMMHM.

2) Error Logs are displayed with Wrong PO.


Solution Analysis and Recommendations

(Include Screen Shots if required)

1) The occurrence is random and no specific pattern could be identified. The issue couldn't be replicated in DEV or QUA environments. It is believed to be caused by a timing issue.

The proposed solution involves putting a time delay of 5 sec while the packing program loops to get each delivery for packing and this is assumed to process the deliveries more efficiently and complete packing w/o skipping randomly.
HOT Martket Program Overview_Updated.jpg

2) Change the Program to read PO's with Item Number to get the correct PO and display in the error logs.

The following are the test scenarios-
Test ID
Test Scenario
Expected Results
SDMM001
Create a HOT market PO as follows-
  • create a HOT market contract with multiple items
  • create 10 call offs
  • create one call off with a delivery block
  • create one call off to deliberately cause packing error
  • execute HOT market program to execute packing for all the deliveries created
Error log should appear correctly for the missed deliveries
SDMM002
Create HOT market multiple PO's for a given contract as above
Error log should appear correctly for the missed deliveries and the correct associated
PO number should be displayed
SDMM003
Execute scenario 1 after making necessary corrections.
No errors should be logged and all the deliveries should be packed w/o skipping
SDMM004
Execute scenario 2 after making necessary corrections-
No errors should be logged and all the deliveries should be packed w/o skipping



Resolution



Release Information


Provide link here to Release Notes if Technical Objects were changed